Optims found while profiling, and dumb benchmark tool

This is just some hacking I did while profiling AE, looking for wasted cpu cycles. In the meantime I needed a way to test small changes and their impact on the CPU in some measurable way, this was the result. It's not particularly pretty, and only useful for internal testing, but it's better than nothing.

The 3 optims address the top 3 cpu consumers on their own. The result of some optimizing was a 5.8% decrease in average frame-time, excluding gpu operations as this was done with d-r+noflip on a static scene.

Just putting this out there for discussion, not for Frodo.