Is it always bad to have an own table for value objects?

I know that value objects should be embedded in the table of the object they belong to but what if the value object is more than a simple object and contains many fields/columns or even sub-objects? I currently have a table named content which in short stores rich text. Since I don't always parse the content I've added a caching system. The table also has a 1:n-relation to another table which contains a list of all the links in the content table. content(content_id[PK], text) content_link(link_id[PK], content_id[FK], object_id) If I would put this data in the orginal table I would follow the rules of database design but many it would make work harder.