I am a Cppcheck developer.
I agree that is a wrong warning.
However Cppcheck preprocess the code. So if you do want to have warnings about real issues then it's inevitable with such false warnings (the conditions are logically the same).
Maybe this check should be activated by --inconclusive, since there can be false warnings when macros are used.
If you can live with the false warning then I'd suggest that you do it. If you want that this is fixed then feel free to write a ticket: http://sourceforge.net/apps/trac/cppcheck/