@fergalbyrne I was concerned about the same, decided to ge this way for it's straightforward implementation and using MultiEncoder. Made some tests https://gist.github.com/breznak/7446953 that confirm this problem. So, I'll tear down the SimpleVector class and make a separate VectorEncoder based on the "for-loop" approach. 

Ad "128bits" I'll have to store the whole "scalar range"-space for each element anyway, wouldn't I? 

PS: the above leads me to.. it's mem-inefficient because we care about order of values, for a set, we could do a very efficient encoding by just overlaying multiple scalar representations ove each other. Do we have that?