ViewProviderAccessDelegate using accessDecisionManager

If an accessDecisionManager is set for Security, isAccessGranted(String beanName, UI ui) will always retrun true and leave the decision to the second hook with the actual object. If no accessDecisionManager is set, the behaviour is the same as before the change and hasAnyAuthority is used whenever there is a @Secured tag.
As I understood the concept SpringSecurityProviderAccessDelegate should be the default approach how to deal with  views secured by the @Secured-tag. The reason I started changing this default approach was because I expected that when I inject an AccessDecisionManager into the Security Bean it will be used for decisions - which was not the case.
I guess one could always just write his own AccessDelegate (though I didn't yet find out how to do this properly :) ) but shouldn't an AccessDecisionManager be used by default if there is one configured?

The situation which made me think there should be a change in the default AccessDelegate was that I simply wanted to add a RoleVoter (because I am lazy and don't want to ensure that every ROLE_ADMIN-User always has ROLE_USER, too). I configured an AccessDecisionManager with RoleVoter and most things worked very smooth - but only the vaadin View security did still reject my ROLE_ADMIN-User, because it didn't use the AccessDecisionManager by default although it was autowired to the Security bean.
At least for me this behaviour was quite confusing.

About configuring: What do you think about extending the @Secured-Tag to allow additional configuration through the annotation?