Binaryread2

[MarcoDorantes]

All tests passed with BinaryReader.ReadChars-based processing.
There is room, of course, to evaluate a different approach entirely StreamReader-based.

[MarcoDorantes]

@xxlxii
All tests so far passed, but there is a problem: there is a breaking-change. All byte parameters now must be cast as char parameters.

[MarcoDorantes]

@xxlxii
Of course, we can avoid the breaking-change by duplicating the whole set of current tests and support previous byte parameters for backward compatibility. Nevertheless, for byte parameters the previous released version can be used still.

[MarcoDorantes]

One of the reasons for the new binaryread2 branch is, in part, because of this referred conversation:
https://social.msdn.microsoft.com/Forums/en-US/77c389ae-1b38-4568-9b97-aeec4c101150/how-to-get-the-encoding-instance-used-by-a-binaryreader?forum=netfxbcl

[MarcoDorantes]

@xxlxii
Besides, maybe we should not be messing around with byte[] and BinaryReader and go all around with char[] and StreamReader. Could we please meet to discuss this before continue? We would need to define the road ahead before even documenting sample cases.

[MarcoDorantes]

@xxlxii
This last commit: 40763db

could be the candidate for the transition from byte[] to char[] for the binary test cases other than the ByteReaderTest1 test case.

[MarcoDorantes]

@xxlxii
As discussed, could you please send the sample files with actual data to be processed by the positional feature?