Possibly not a bug: With Insert + IMCE, a removed image is still stored elsewhere and can not be deleted.

Background: I am using Insert + IMCE on drupal 7. I edited an image I had previously inserted into a node with Insert (from the IMCE file browser), then uploaded the image via IMCE. When I go to the node I can not get the "new" (edited) version of the image to show up, regardless of removing it and then searching for it again via IMCE file browser. Even on differnent nodes Insert only sees the "old" version. I removed the image, deleted the node, and tried to recreate the node, but Insert still only sees the "old" version. I even tried to delete it via IMCE, but got a message that the image was in use from another application (I'm assumed Insert). Clearing cache, running cron, nothing worked.

Finally I found that this "old" image is stored in public/styles/medium (the style I had originally used via the Insert module). I deleted it there, then went back to my node, and Insert showed the new image instead.

So, my specific problem is solved, but I think the whole "can't delete an image" thing is a possible can of worms for users. I wonder: if I had abandoned this and just decided not to use the image any more, would I have ever been able to delete this image? Seems the integration of these two very good modules may lead to undesired behavior.