1st I must say, I am a huge fan of this tool, saving my days again and again.
Currently v0.9 (and other variants) still blocks the image write back, if image size indicates smaller than current CF/SD card. This is the only draw back that I feel important to fix.
This is a problem for embedded system developers/admins (who I believe use this tool more often than others) when different brands/models often have their sizes tens/hundreds of MB different. E.g, Kingston even have two generations of 4G CF cards of different sizes.
I believe we all want the warning/err dialog box to have an option to continue, to force restore/clone to smaller card. Then we can work on our own work flows, ensure we only partition CF/SD card to use only a reduced size (say put partitions in first 3.4G instead of full 3.8/4G of whole card), by reserving a tail zone of unused. Then this restore/clone allow developers just to cater for card variants, say a Android devel 8G img maybe should contain only 7G useful partitions, but then applicable to all 8G variants SD/microSD models available.
Gotta say, with this feature in, it's already perfect 1.0 for me.