Replaced read-line with a read-until implementation to allow arbitrary
row-separators

Thanks Dimitri Fontaine, dimitri@github
tried a read-into-buffer-until parsing strategy, but it seems slower than read-until :/

re #13
re Programming:#1201 (3)
optimized read-into-buffer-until, added test to check its speed
against: read-line & read-sequence

Its currently twice as slow as read-line and 3 times slower than
read-sequence.

re #13

Time on yesterdays commit didnt go through because I fumbled the
ticket number
re Programming:#310 (4)
print statistics instead of returning them (where they are invisible)
tried copying SBCLs "fast" implentation of readline (which is a branch
inside of READLINE)

This seems to be using rewindable streams and buffers to make readline
faster than read until, I was hoping that by using this implementation
I could see the same performance, but for whatever reason this seems
twice as slow :/

re #13

Programming:#310 (1.25)
added some declarations that bring fast-read-into-buffer-until inline
with sbcls own read-line function

re #13
re Programming:#310
type optimizations
merged master changes
Use read-line if we can, otherwise use read-into-buffer-until

 * Handle newlines that span buffers
 * removed sbcl specific fast-read-until (too complex and used private
   stuff)
added missing line-endings,csv tests file