It should be noted that performing your comparisons using multiple Boolean variables means that you cannot take advantage of short-circuit evaluation.

VS2012, compiled with default release mode settings:

..

Resulting disassembly:

...

Compilers are very, very smart.

They are, hopefully, also very smart not to do that when the evaluations of the temporary variables have side effects because that would change the meaning of the program. Your example works because the individual conditions does not have any observable side effects. If the expressions have side effects, or otherwise relies on short circuiting to prevent the evaluation of an expression in the condition (for example checking for null-pointer before accessing a member of an object), expanding the expressions to temporary variables before the if-statement won't work.

OP's code does not include side effects.

On the other hand, in the case that the statements do (or may) have side effects, the compiler will obviously not screw it over.

In that case, though, it's better to just write the test sequence out clearly rather than relying on obscure details of the spec. If you want to do something obvious like null checking, you can just do that into the temp:

bool a = (ptr && ptr->something);
bool b = stuff;
if(a || b) {etc}

That's just begging for a long debug session some time in the distant future. Stuff like that is hard to spot if you aren't looking for it.

bool execute = false;
if(value > 0) {execute = true;}
else if(SomeExpensiveComputation()) {execute = true;}
if(execute) {std::cout << "Example 1" << std::endl;}

^ Compiles the same, but is far more clear about what's going on.

Alternatively, it may be a good idea to at least leave a comment indicating that you're making use of a short circuit.