Me, because it's not opinion, and I have demonstrated repeatedly that what I'm talking about are ancient hominids, but your examples are of sea life.
It makes no difference what organisms you use as examples, as the theory underlying morphological and genetic phylogenetics is identical for all organisms. When I taught introductory systematics many years ago, we used screws, nails, and bolts to collect characters from, and the methods work exactly the same. Your apparent contention that the choice of example organisms should make a difference is spurious, not to mention highly unscientific.
The subjectivity of genetic analysis that Kotatsu is talking about is based on what his experience was nearly a decade ago, and while he may have a point about the nature of human bias, I still think DNA will give you more information than morphology if you have it.
Certainly it will give you
more information. It will not, however, automatically give you
better information. Sequencing a dozen genes is a few days work, and may give you a few thousand characters. Getting a few thousand characters through morphology will take years, so certainly there is an advantage to genetic characters.
However, as I've said above, what you are really looking at when you use genetic material is the morphology of individual molecules associated with that organism.
There is no difference. Genetic data is not a separate class of information from morphological data, it is simply morphological data of smaller components of the organism. Here is the progression (roughly):
1. I can look at the overall structure (whole-organism level: number and arrangement of appendages, symmetry, coelomic structure, etc.);
2. I can look for certain diagnostic structures (overarching organ system level: absence/presence of whole organ systems, etc.);
3. I can look at the gross morphology of the structures present (organ system level: chaetotaxy, dental patterns, scutellation, skeletal structure, etc.);
4. I can look into any of these organ systems and focus on single organs (organ level: structure of renal systems, structure of eye, etc.);
5. I can focus on the more detailed structure of these organs (supercellular level: essentially, what cells are present and how to they relate to and interact with each other?);
6. I can zoom in on the individual cells (cellular level: what components exist in the cells of this organ?);
7. I can focus on organelles inside the cells (intracellular level: what proteins are expressed in these cells?);
8. I can focus on part of one of the organelles (the DNA) and study its overall structure (chromosomal level: essentially karyotypes);
9. I can look at gene order inside the chromosomes;
10. I can look at individual genes (genetic analysis).
All of these things are morphology, but focusing on different levels. There is no qualitative difference in studying the morphology of the smallest structure in the organism and studying the largest structure, the data you get is of exactly the same sort, and it is coded in exactly the same way into the programs we use to construct phylogenies. PAUP* does not inherently know what your data is coming from, as long as it is written in a form it can understand. If I construct a morphological data set, I am free to code the various character states as I want. If I want to use ACGT as my annotation instead of 0/1/2/... that is my prerogative, and the programs don't care (1).
ACGT is simply shorthand for a morphological structure. It just happens to be the case that we can normally express the morphology of a molecular in a limited, regular way. The same is not true of most other systems of morphology in organisms, as these are generally more varied. We could certainly make similar annotation systems for other groups of morphological characters, such as chaetotaxy, but they would not normally be as elegant as ACGT.
---
(1) Unless your program reacts on stop codons, in which case you can just rearrange your morphological matrix so you don't get stop codons.