Hi, I'm currently evaluating Esenthel for a project I'm working on, and I just had a couple of thoughts.

I'm wondering whether it would be worth while producing different versions of the static library? For example, one linked to the debug C++ runtime, one linked to the DLL C++ runtime, etc? I know it's more work, obviously, but it's also a bit more flexible in terms of deployment (for example, I've got to link my game to the release C++ runtime, and then I miss out on all the built-in memory leak detection stuff, etc...)

Um... that's actually the only question I can think of for now :-)

I don't think I'd enable that in the nearest future, it would be a little too much trouble.

you can enable engine's memory leak detection, it doesn't point you to the line of code, but returns the number of memory leaks. (see App.flag)

but if you're using memory containers (Memb/Memc,..) having memory leaks shouldn't really happen