Actually, on further examination, this appears to be fixed in 2.0.16. This issue will be closed. Kurt