That assumes that your code hasn't in the meantime added another list item
to the list view and that the memory manager hasn't coincidentally re-used
the memory of a previously freed item when allocating the memory for the new
item ...
Yes, this is going to be a rare occurrence... freakishly
You can lead a horse to water, but you can't make it drink.
That assumes that your code hasn't in the meantime added another list
item to the list view and that the memory manager hasn't
coincidentally re-used the memory of a previously freed item when
allocating the memory for the new item
