Hi, sorry for the late reply...
.NET applications do look like they use more memory, but this is not really "used" memory, but "reserved" by the .NET Framework memory management. If the system needs more memory, it will reacquire that memory, which is not really holding data. A good portion of those 50 megs would never get swapped to the disk pagefile (this is costly), and can be allocated to other processes by the system if needed.
I do have memory usage in mind when working on slimKEYS. Currently, the single place where I'd like to put some more effort on memory usage, but foremost CPU usage (on slimKEYS start-up only) is with slimLAUNCH.FileSystem. Another version could see an improved caching system, and I definitely want to support the Windows Desktop Search API with another similar plug-in.
Hope this helps.