>Nice. Any idea what the overhead is for the run-time
>performance checks? Seems like something you'd eventually
>want to disable once you clean up all the current problem
>functions. Then just enable it periodically to see if any new
>ones have started misbehaving.

Right now it seems negligible (set a clock_t before calling the function, set a clock_t after calling the function, subtract the clocks and compare against the goal, and report).

I'm actually inclined to leave them in if the overhead continues to prove to be minimal, because I'd rather have some checks in for new code that gets added without having to code review everything anyone checks in, and I'd be curious how some of these functions scale based on the number of players online.