title: Defining WIN32_LEAN_AND_MEAN increases build times
body: <p>I am noticing something strange when working with the win32 api. I am working with a small project, and I tried adding a define WIN32_LEAN_AND_MEAN right after where I include windows.h. Using the build time tracker in the build logs of VS 2013 RC, the build times are actually taking longer (10ms or so more) with define WIN32_LEAN_AND_MEAN enabled. Am I defining WIN32_LEAN_AND_MEAN in the right place? Is the time spent running the preprcessor defines shorter than the time than just looking at them? If so, at what size of a project should you define WIN32_LEAN_AND_MEAN? Thanks for the help!</p>
  
  <p><strong>Update</strong>: I chaged my define WIN32_LEAN_AND_MEAN to before incuding windows.h, as advised, and it gave me a even larger performace impact. It cost me 260 ms in build time. </p>