Why use explicit cursors instead of regular loops?
The code you posted is using a cursor.  It is using an implicit cursor loop.

There are cases where using an explicit cursor loop (i.e. declaring a CURSOR variable in the declaration section) produces either cleaner code or better performance


If you have more complex queries that you can't refactor out into views, it can make the code easier to read if your loop iterates over student_cursor rather than including a 30 line SQL statement that embeds a bunch of logic.  For example, if you were printing out all the students that were cleared to graduate and that involved joining to tables that had their academic records, the requirements of their degree program, tables with information on academic holds, tables with information about overdue library books, tables with information about unpaid fees, administrative overrides, etc. it would probably make sense to refactor the code so that this query wasn't stuck in the middle of code that is concerned with presenting the list to a user.  That might involve creating a view that would encapsulate all this logic.  Or it might involve creating an explicit cursor that was declared either as part of the current PL/SQL block or in some higher-level PL/SQL block (i.e. a cursor declared in a package) so that it is reusable.  Or it might involve doing something else for encapsulation and reusability (say, creating a pipelined table function instead).
If you want to make use of bulk operations in PL/SQL, you generally want to use explicit cursors.  Here is a StackOverflow thread that discusses the performance differences between explicit and implicit cursors.  If all you are doing is calling htp.prn, doing a BULK COLLECT probably doesn't buy you anything.  In other cases, though, it can result in substantial performance improvements.