No that is the latest version.
I panicked because I did manage to replicate the problem, but only on a test site running the very latest beta code.
But the cause in my case was a corrupt set of GEDCOM data, caused by too many experiments during testing with the new (next release) renumber and append trees feature.
A quick re-import of my GEDCOM file fixed all the errors. I have also checked a few other sites running 2.0.2 and none show that problem.
Where did that GEDCOM snippet you posted come from. Was it a GEDCOM file or the raw GEDCOM edit screen?