We managed to fix this for 2.0.1 after all, so it should be corrected in the release version that gets posted in a day or two.
