@ISIWARE,
We have tested the scenario and managed to reproduce the same issue at our side. The problem line of your code which causes the unexpected behavior is the one with document.UpdateFields() method.
For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET - 22978. You will be notified via this forum thread once this issue is resolved.