in reply to module memory usage

First, a couple of remarks:

I do not know of a standard way of accessing this data, but when I have a need for it, I usually run top (or equivalent resource monitor for other systems), and execute the code to see how much it takes up. You can make it a little easier by sending out some messages about what the program is doing (i.e. which modules are being loaded) and then sleep()ing for a couple of seconds. I haven't found a real need for anything more sophisticated.

YMMV
Joost.