Personally, I adopt the coding policy document that I have to abide to at work, its easier than having two different standards for my own projects and work projects.

Whilst I can't for obvious reasons post the 100+ page document, a few things from memory that are differnt to your standard:

All class variables start with m_ (for member), to distinguist them from local variables and method parameters.
There are variable prefixes, but they don't match your list - instead of underscore, we use camel case. eg. 'bAbort' is a boolean variable, 'iCount' is an integer variable (unsigned/signed doesn't matter). String is 's' regardless of class. A null terminated string (eg. char * or char[]) is sz (eg. szTitle).

We use autocompletion, so the above helps shorten the list too, so when you see a function requiring a null terminated string, you can just type sz or m_sz depending on the scope you want. All class variables must be documented regardless of whether there usage seems obvious or not, local variables not so much. These comments show up in the autocompletion window to help you make a decision.