- SocketAsyncEventArgs have lots of state on them and as a result are quite big (~350) bytes at runtime. We can pool these since sends are usually very fast and we can reduce the per connection overhead as a result.
- We also allocate one per IOQueue to reduce contention.
- Fixed buffer list management
- Disposed pool when the transport is disposed
- Added project to slnf so running tests in VS was possible
- Clear the buffer and buffer list before returning to the pool
- This cleans up dumps as the pooled senders don't see references to buffers
while pooled in the queue

…ction.cs

Co-authored-by: James Newton-King <james@newtonking.com>

- Keep track of items in the pool separately from the queue count.
- Clear the buffer only if the buffer list is null

…ionFactory.cs

Co-authored-by: Brennan <brecon@microsoft.com>

…rPool.cs

Co-authored-by: Stephen Halter <halter73@gmail.com>