I can confirm this has been fixed comparing the output of 0.4.8.2016 to that of 0.4.8. Thanks very much.