title: Why is Socket's Available > 0 just after being returned from AcceptAsync()?
body: <p>I'm encountering this weird issue whilst working with .NET High-Performance Sockets.
  Just after I get a new Socket via an AcceptAsync() op, <strong>the [Available] property is equal to some non-zero value</strong>, usually 64. At a closer look, I can see that all the available bytes' values in the Socket's buffer are set to 0.</p>
  
  <p>Client-side, the only operation ran is ConnectAsync(). No SendAsync(), no nothing.</p>
  
  <p>That holds regarding of Nagle's enabled state.</p>
  
  <p>Anyone ever encountered this issue?</p>
  
  <p>P.S.: I will update &amp; post some code if needed, but it's kind of a big snippet.</p>