Added some pseudo-hacky speedups to the TCP reporting to try to get to the bottom of some of the out of memory issues I've been seeing.  Basically, reports aren't getting processed fast enough, and the incoming report queue balloons until all the memory is used.  Definitely there is huge room for optimization because the previous implementation demarshalled an entire report.  For now I did a hacky thing which is hopefully good enough for my experiments...