Variant: refactor of the shared field api

* shared fields api now behaves like the individual fields api (creates an object but doesn't make any copies)
* SharedField class is iterable and can hold multiple values
* special cased boolean_shared_field to return a single bool (since * vector<bool> is impossible by spec)
* current API (as well as the individual field API) relies on missing() checks before using the values. Dereferencing a missing shared field will segafult -- see #166
* add check for dereferencing an empty field (throws out of range exception instead of segfault)

fixes #151
Have you actually benchmarked this to back up this claim? I would actually expect a single iteration that updates multiple bitsets (or counter variables, etc.) simultaneously to outperform multiple separate iterations each updating a single bitset. Remember that the cache is big enough to hold multiple values at once...