Fixes #99

Description of changes:
Updates TCPClient to do a single-byte, non-blocking read after making a write to make a best effort to detect when our write might have been made to a closed socket.

• TCP sockets won't usually throw a pipe broken exception until a non-empty read request is executed against it.
• Had to switch to using SocketChannel in order to be able to do a non-blocking read.
• Chose to do the read after the write attempt because that ensures that this write was actually sent instead of potentially silently failing.
• It is technically possible for a metric to be double-sent if there is a race between the write and read.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.