Testing management strategy for Unit coverage test

I have a question about a work what I am doing. I recently changed my work to software white-box tester from software developer. I am leading little part as a leader and the part is in a software development team. A team manager gave me a goal to set up a software white-box test process. Main work of a part is to find bugs using static and dynamic testing tools, such as Polyspace and VectorCast.

I am enjoying when I test software using Polyspace since analyzing the reason from detected error needs knowledge of coding and also it makes language skill up. However I feel wearisome and uncomfortable when I do unit coverage test based on source code. I think making test cases to only feet code coverage, statement and branch coverage, doesn't need high quality skill. Making test cases is repeated task and it spends much time as I see it.

I think Knowledge of essential C language is enough to do this work and using university graduated workers for this work is waste of valuable resource. So I'm gonna suggest to hire part-time workers for this job to my team leader. I think its batter to review unit test case and coverage from part-time works and manage each test project and also spend more time to review source code. It seems more worth and helpful for good software quality in my opinion.

Here is my question. Is my opinion common in this area? I want to know how other companies are managing this work and having strategy of source code test. Does your company also hire highly educated workers to make test case which meet 100% of branch coverage?