You could just remove it (and rely on you source management system to get it back) or you comment it out (where you will at least get syntax highlighting to help you spot the dead code).
It happened multiple times to me that I missed a tucked in &&false while I was porting older code to a new API. As the code was disabled anyways, I could have spared myself the time of patching it up.
Now sure, if you are just testing something during development, this might be a viable way to disable code, but something like this should not be committed. Please use proper comments or better, just remove the code.
In this light I don't understand why the article is even trying to suggest syntactical "improvements" (adding parentheses doesn't make it more readable IMHO), when the complicated expression should have just been rewritten to
UINT uFlags;
uFlags = DST_ICON | DSS_NORMAL;