Change list

I assume I've finally found the reason for the extensive memory usage described in #2119

Each proxy class created by ByteBuddy gets automatically cached by the
given class loader. It is important to have a custom cache in order to improve
the performance and to avoid extensive memory usage for our case, where
the amount of instrumented proxy classes we create is low in comparison to the amount
of proxy instances.

Types of changes

• No changes in production code.
• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)