hmm, you know, I really like this idea. Mostly because it will also help to discover flaws like what appears to be affecting titi's 32 bit build of 0.2.8. Of course, we can always do a profiling build and run that through gprof to see what's eating what, but I like the idea of having a performance monitoring mechanism built into the game that's designed around the important checkpoints, when we enter functions for specific reasons. I might be able to squeeze most of this out of gprof if I would just learn to use it better, but I think that having a class & object perform this, with code that "compiles out" of a release build would be a wonderful idea. Also, I can use -O3 (with inlining) and still get good profiling data.