Here a short update from my side:
Talked the Peter, he confirmed that he had a similar situation with the ~v variable marker. After filing a bug report Adobe mailed me for more information on the subject in question.
Working around that problem isn’t the question of this thread, of course it is very easy to come up with the desired solution and I already did ? The only question for me is why this wasn’t already fixed long ago and my guess is that it has to do with an incomplete implementation…