With this definition, any loop of the form for( conformation::Atoms::const_iterator blah = res.sidechainAtoms_begin(); blah != res.heavyAtoms_end(); ++blah), will SKIP iterating over the LAST heavyatom in the residue. From my understanding of the iterator concept, the end iterator should always point to one past the last element to be accessed.
We don’t keep a public-facing changelog to that depth. There is a broad-scope new modules list with the releases sometimes. We are considering going to weekly releases; we may integrate that with the bug tracker and do a weekly bugs-fixed-list, but it seems only medium likely.