Sorry that I provided my help, I will refrain from doing so in the future.

You should always use prefix in/decrement. x++ is x = x + 1 which means that a temporary copy of x needs to be created which is then raised by one and copy over to the original adress. While ++x is just "Go to address of x and raise by one". While this doesn't really affect ints and similar, it will however get very cpu consuming if in/decrementing non-primitive types. So you should always use prefix for a simple reason: to not get used to postfix, even on primitives (even Stroustrup, the C++ inventor, will tell you this, He even says that the language should from a programmers POV really be called ++C instead - but it doesn't because C++ simply sounds better).

I removed some unused variables (why waste memory and cpu time for them?), but not the function calls that assigned them a value, because maybe these calls were needed (as I said, I did not set up a build environment and tested things and checking what these functions do, that's why I only did the easy hacks now).

You should never create variables because "you maybe need them in 100 years". You will forget about (most of) them (->wasting memory and cpu time to create them at runtime).

BOOL is just "typedef int BOOL", the proper way of converting an int to bool is this:
bool b = (BOOLvar != 0);

Bye.

> OK, I fixed the easy ones

What about the rest of Anonymous' contribution though? You looked through it, is there something we can make use of?

At the very least, if he detected memory leaks and possible null pointer exceptions with this tool, we should definitely go after them.