title: When profiling in Release build mode, is the generated code really Release-build-mode-optimized?
body: <p>I'm wondering: When .Net generated stack traces in a Release build when throwing exceptions, the line numbers are often off, also some stack frames that should exist when analyzing the source code are not even printed because they - presumably - got optimized away.</p>
  
  <p>So when Visual Studio says a lot of time was spent in method X when CPU sampling a release build, can this be trusted or could it also be off due to optimizations?</p>