As for the join example, you compare a table join against a single lookup... not the same thing. How many seeks would objectivity need to find the phone number for the employers of all aunts (on the fathers side) of every person in the database (which is what a join is for)? And as for the virtual addresses, Oracle (for example) can use raw disk access to optimise the layout of data on the disk to minimise head movements when executing common queries. It can do this because relational algebra hides all details of the implementation from the user, allowing the database code more freedom to choose how it stores and processes the data).
So you can either use object modelling and and ORM/NoSQL, or relational modelling and relational-algebra/SQL. Of the two relational modelling is more powerful (can model more situations), and relational-algebra is a higher level language (because you specify what you want done, not how to do it).
To make this even more thought provoking, what if the virus detector is infected. What if the 'C' compiler is infected, such that all programs it generated automatically are infected, and cannot detect the infection. If the infection is not spotted soon enough, all virus detection products compiled with the compiler will be infected. What if this has already happened?
For reference a "Field PG" is a machine used to program the PLCs not the actual target of the infection.
"Once Stuxnet had infected a computer within the organization it began to spread in search of Field PGs, which are typical Windows computers but used to program PLCs. Since most of these computers are non-networked, Stuxnet would first try to spread to other computers on the LAN through a zero-day vulnerability, a two year old vulnerability, infecting Step 7 projects, and through removable drives. Propagation through a LAN likely served as the first step and propagation through removable drives as a means to cover the last and final hop to a Field PG that is never connected to an untrusted network."