MSVC optimizer failing due to a few using statements.

[rcrowder]

PR #709 added a variety of serialization related changes. Two of those commits [1, 2] causes the Microsoft Visual C compiler/optimizer to fail. Scott had a comment answered [3] on why using Serializable::write; was added to the Spatial Pooler. And for most of those additions everything looks ok, but for some reason adding them to SparseBinaryMatrix and SparseMatrix throws an unknown exception when using the Visual C compiler.
Removal of the using lines (for both read and write) allows the MSVC compiler to build the nupic.core library correctly, but I'm unsure of what implications there would be if those lines are removed there. I'm guessing something with the setup of SparseBinaryMatrix and SparseMatrix is different than other setup in the PR changes?

ref https://discourse.numenta.org/t/nupic-core-compile-error-in-windows-64bits/995

1 e221e3d
2 5ffb053
3 #709 (comment)