If CH vehicle profile is not the first the access limits are not considered

[karussell]

It seems that a CH profile which is on the second rank of a profile list or later does not take access limits into account. Disabling CH helps and also moving it to the first rank of the profile list. This problems is independent of the used graph.bytesForFlags

Hmmh, cannot reproduce this in a test environment, seems to be something different ...

[karussell]

Ok, strange. This is something specific to a custom encoder. It does not look like the same problems happen for e.g. car. Hmmh, still we need to improve the API to avoid this for custom encoders.

[karussell]

Arg, it is a duplicate of #490 and the reason is the contains() check ... e.g. think about the flag encoder names 'car' vs. 'electric_car' ...