The problem was confirmed and fixed with a new driver on RME's side (within 3 days of reporting the issue... on a weekend... wow).
(EDIT): Apparently I don't have privileges to post links until I log another 13 posts...
The RME forum thread and the new driver can be found via gswitz link on reply 2.
Or Google: RME Yikes
And it should be first on the list.