Variable size objects are addressed at the very end of the post: "Support for variable-sized objects requires a separate cyclic list for each size...".
> That implies that you have to divide up the memory ahead of time into an area for each size?
No, it doesn't, as it maintains linked lists of objects, so you can use any underlying allocator to feed you objects to add to the different linked lists.
Languages with only one object size are not exactly in vogue at the moment, so this is a major limitation.