Float precision used for daughters_ branches (and maybe mothers_ as well) causes the mass values computed downstream using TLorentzVector to be different from the original value.
Probably not an issue because nobody uses the mass as a variable, but appears as differences in the synchronization. Note that this does not affect SVFit computation.
To be changed to double after the rest of the downstream codes are ready to handle vectors of doubles.