I'm assuming it takes the measurements during a single tic immediately following the execution of the command. If correct, this poses a bit of a challenge in the following cases:
1) If I have some randomization written in the actor's functionality, which alters the CPU usage by the actor, the readings will fluctuate on subsequent executions. For example, average 0.002500 ms / actor on the first try, 0.003100 ms on second, 0.002120 ms on third, and so on. I suppose there is no way to take an averaged measurement over, say, 10 or 35 tics?
2) I know this is a rather broad question, and hard to answer comprehensively, but how would you catch some random CPU-intensive event during the play, using either profilethinkers or something else? Is the only option to simply make an educated guess on what might be the cause, and then for example, explicitly setting up a test where the event happens immediately on firing of a test weapon, and catching it by binding "profilethinkers; +attack" into a (keyboard) key?
I don't mean to appear too demanding.
I certainly appreciate and consider the feature very useful even without the above possibilities.
