It is a onetimer, I must admit that, but I just noticed that when I do multiple find and replaces (solution wide in this case) that an old value was used as a replacement string instead of the newly added one…
bug confirmed, global search behaves not always correct
global search and replace is overhauled in 3.1. Now it works much better then before.