anchor.diff:  over `n` classes (`Person`, `Company`, `Order`, ...)'s `m` getters (`getName()`, `getAddress()`, `getBirthDate()`, ...),
   so how can a JPA implementation have `n * m` static fields without knowing `n` nor `m` at compile time?
   
  -I do hope that MethodHandle will become as fast as direction access in future Java versions, replacing the need for...
  +I do hope that MethodHandle will become as fast as direct access in future Java versions, replacing the need for...
   
   === Generated code with javax.tools.JavaCompiler
   
  
positive.code: ** another 1000 calls to `Person.getAddress()`
  * Similarly, if you write 1000 different persons to XML or JSON, there are likely 2000 calls by XStream, JAXB or Jackson.
  
  Obviously, when such code is called x times per second, *it's performance matters*.
  
  == The benchmarks
  
  
negative.code: 
      private final MethodHandle getterMethodHandle;
  
      public MyAccessor() {
          MethodHandle temp = lookup.findVirtual(Person.class, "getName", MethodType.methodType(String.class));
          temp = temp.asType(temp.type().changeParameterType(0 , Object.class));
          getterMethodHandle = temp.asType(temp.type().changeReturnType(Object.class));
      }
  
      public Object executeGetter(Object bean) {
          return getterMethodHandle.invokeExact(bean);
      }
  
  