Windows Performance and Memory Usage

On windows, when user has defined onNewFrame and did NOT define onFrameChanged and onImage, then an opportunity for skipping memory allocations and skipping the copy of images is available.
This leads to about a 25% increase in the number of frames that can be captured and memory usage is cut in half.

This is ONLY available if onNewFrame is defined the following functions are NOT defined: onFrameChanged; onImage.

Will implement Mac and Linux implementations next