up for pier review 
Do you have some test code you can provide, that shows intended usage?
class CResbufList //derive from CObject or not??
Gut says not.
At first I wasn't to crazy about, as it seemed a bit over baked and heavy for dealing with resbufs, but looking at it closer it has potential. So these comments are purely after looking at it for about 15 minutes.
1) Eat the dog food you give your dog. You provide the user of the class an iterator of begin() and end(). Use these in your loops as well, for instance the functions CResbufList::at, clone, and others. You'll ensure they work as intended as well as provide users of the code ready made examples on how to use them.
2) Maybe add a size function to the class? Sorry just saw the length function, not a very good function name to conform with the std.
3) CResbufList::at and removeAt, kind of useless function taking size_t input parameters as there isn't a find function to know what index to delete.
4) CResbufList::at and removeAt, more useful if they took pointers or iterators at input parameters. (edit: added iterators)
5) Maybe add an insert function.
6) By inference of cloneNode your copy constructor and assignment operators are not exception safe. Make sure you check all API return codes and pointers, you've got a few de-referenced pointers that are not checked first.
Otherwise looks good Daniel.