title: Is Resharper unnecessarily warning me about Access to modified closure here?
body: <p>...so I have this code:</p>
  
  <pre><code>        foreach (var entry in list)
          {
              var marginOneEntry = otherList.FirstOrDefault(p =&gt; p.Margin == entry.Margin);                
              if (marginOneEntry == null) continue;
              // Do stuff with marginOneEntry
          }
  </code></pre>
  
  <p>and Resharper 5.1 warns me about "access to modified closure" for the use of <code>entry</code> in the compare-statement in the lambda expression. Isn't the FirstOrDefault-call cancelling this issue? Is my code bad or is this warning just a shortcoming in Resharper?</p>
  
  <p>Note: I have read other topics on Access to modified closure here on SO, but I want an answer for this specific case, and to get clarified whether or not Resharper is overly sensitive on this subject.</p>