Can Interlocked.Increment overflow cause .NET runtime corruption?
<p>The MSDN documentation for <a href="https://msdn.microsoft.com/en-us/library/dd78zt0c(v=vs.110).aspx" rel="noreferrer"><code>Interlocked.Increment</code></a> states:</p>

<blockquote>
  <p>This method handles an overflow condition by wrapping: if <em>location</em> = Int32.MaxValue, <em>location</em> + 1 = Int32.MinValue. No exception is thrown.</p>
</blockquote>

<p>What does “<em>location</em> + 1” mean in this context? If <code>Increment</code> alters the memory location next to the <em>location</em> field, isn't this likely to lead to corruption in the .NET runtime, given that this adjacent location could be anything (object references, class metadata, etc)?</p>