In DistanceTable implementations Memory pool and Container element type must match but are defined via different type aliases or template parameters.

This is a bug in waiting it doesn't cause an issue yet.

agreement between template parameter T and RealType in distance tables only coincidentally matches.
See
`SoaDistanceTableAA` and related classes.

This occurs do to excessively long and somewhat arbitrary type alias chaining through the class hiearchy #913. I believe that if this fell out of agreement code could still compile but seriously off memory accesses could occur.

The fix is probably as simple as just making the memory pools of type T and not RealType. Then reviewing whether use of RealType from down in the inheritance chain really makes sense.